home *** CD-ROM | disk | FTP | other *** search
- Path: arlut.utexas.edu!usenet
- From: Lee Crites <crites>
- Newsgroups: comp.lang.c++
- Subject: Re: STL compilers for SUn?
- Date: 18 Jan 1996 02:47:02 GMT
- Organization: Applied Research Laboratories - The University of Texas at Austin
- Message-ID: <4dkcb6$a90@ns1.arlut.utexas.edu>
- References: <4cube1$qv4@pheidippides.axion.bt.co.uk> <JARNOT.96Jan13014901@box10.dstar.iddis.com> <ROUQUETT.96Jan17004956@overcat.jpl.nasa.gov>
- NNTP-Posting-Host: squid.arlut.utexas.edu
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 1.1N (X11; I; HP-UX A.09.01 9000/730)
- X-URL: news:ROUQUETT.96Jan17004956@overcat.jpl.nasa.gov
-
- rouquett@overcat.jpl.nasa.gov (Nicolas Rouquette) wrote:
- >Indeed, I routinely use the old Sun C++ 4.0.1 for SunOS 4.x porting
- >and the new Sun C++ 4.1 for development on Sol 2.x. However, I haven't
- >tried the raw HP code; instead, I use Object Space's STL<Toolkit> and
- >Systems<Toolkit>. In term of falling behind, that may be true in C++
- >when the version cutoff of various companies aren't quite in sync with
- >the latest draft revisions; but that's a property of C+ not being ANSI
- >yet. However, feature-for-feature, I'd be surprised to find a PC
- >compiler that won't choke on what the brave and trusty Sun C++ 4.1
- >does.
-
- I have to agree with Kevin here. I prefer to do my development with CC on our
- sun whenever possible. This time, though, it just isn't.
-
- I *am* using the '...raw HP code...' version of the STL, as well as the one
- from Mark Nelson's excellent tome _C++_Programmer's_Guide_to_the_STL, and I
- can't get the 'ole girl to compile even the simplest of tests. The same code
- compiles without changes on our RS6000, HP700, and pc (borland, of course).
- I'd love for someone who *has* been able to get the STL code to work on their
- sun to let me know what they did, because, as I said, I prefer to use it.
-
- Lee
-
-